Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: print port in the logged error message after failed WS connection with EADDRINUSE #19212

Merged
merged 1 commit into from
Feb 4, 2025

Conversation

Andarist
Copy link
Contributor

Description

This is just a small QoL improvement, following the same error message as the one reported here:

reject(new Error(`Port ${port} is already in use`))

@Andarist Andarist changed the title Print port in the logged error message after failed WS connection with EADDRINUSE chore(vite): print port in the logged error message after failed WS connection with EADDRINUSE Jan 16, 2025
@patak-dev patak-dev changed the title chore(vite): print port in the logged error message after failed WS connection with EADDRINUSE feat: print port in the logged error message after failed WS connection with EADDRINUSE Jan 16, 2025
@patak-dev patak-dev added the p2-nice-to-have Not breaking anything but nice to have (priority) label Jan 16, 2025
Copy link
Member

@sapphi-red sapphi-red left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@sapphi-red sapphi-red merged commit 14027b0 into vitejs:main Feb 4, 2025
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p2-nice-to-have Not breaking anything but nice to have (priority)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants